View M29W320DB70ZE1F_5452881.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

march 2008 rev 10 1/56 1 m29w320dt m29w320db 32 mbit (4mbx8 or 2mbx16, non-uniform parameter blocks, boot block), 3v supply flash memory feature summary supply voltage ?v cc = 2.7v to 3.6v for program, erase and read ?v pp =12v for fast program (optional) access time: 70, 90ns programming time ? 10s per byte/word typical 67 memory blocks ? 1 boot block (top or bottom location) ? 2 parameter and 64 main blocks program/erase controller ? embedded byte/word program algorithms erase suspend and resume modes ? read and program another block during erase suspend unlock bypass program command ? faster production/batch programming v pp /wp pin for fast program and write protect temporary block unprotection mode common flash interface ? 64 bit security code low power consumption ? standby and automatic standby 100,000 program/erase cycles per block electronic signature ? manufacturer code: 0020h ? top device code m29w320dt: 22cah ? bottom device code m29w320db: 22cbh ecopack ? packages available fbga tsop48 (n) 12 x 20mm tfbga48 (ze) www.numonyx.com
contents m29w320dt, m29w320db 2/56 contents 1 summary description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2 signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1 address inputs (a0-a20) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2 data inputs/outputs (dq0-dq7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3 data inputs/outputs (dq8-dq14) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.4 data input/output or address input (dq15a?1) . . . . . . . . . . . . . . . . . . . 12 2.5 chip enable (e) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.6 output enable (g) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.7 write enable (w) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.8 v pp/ write protect (v pp/ wp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.9 reset/block temporary unprotect (rp ) . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.10 ready/busy output (rb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.11 byte/word organization select (byte) . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.12 v cc supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.13 v ss ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3 bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.1 bus read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.2 bus write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.3 output disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.4 standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.5 automatic standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.6 special bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.6.1 electronic signature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.6.2 block protect and chip unprotect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4 command interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.1 read/reset command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.2 auto select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.3 read cfi query command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.4 program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
m29w320dt, m29w320db contents 3/56 4.5 unlock bypass command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.6 unlock bypass program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.7 unlock bypass reset command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.8 chip erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.9 block erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.10 erase suspend command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.11 erase resume command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.12 block protect and chip unprotect commands . . . . . . . . . . . . . . . . . . . . . 21 5 status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.1 data polling bit (dq7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.2 toggle bit (dq6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.3 error bit (dq5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.4 erase timer bit (dq3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.5 alternative toggle bit (dq2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 6 maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7 dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 8 package mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 9 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 appendix a block addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 appendix b common flash interface (c fi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 appendix c block protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 c.1 programmer technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 c.2 in-system technique. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 10 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
list of tables m29w320dt, m29w320db 4/56 list of tables table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 table 2. bus operations, byte = v il . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 3. bus operations, byte = v ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 4. commands, 16-bit mode, byte = v ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 5. commands, 8-bit mode, byte = v il . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 6. program, erase times and program, erase endurance cycles. . . . . . . . . . . . . . . . . . . . . 24 table 7. status register bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 8. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 9. operating and ac measurement conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 10. device capacitance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 11. dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 12. read ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 13. write ac characteristics, write enable controlled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 14. write ac characteristics, chip enable controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 15. reset/block temporary unprotect ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 16. tsop48 lead plastic thin small outline, 12x20 mm, package mechanical data. . . . . . . 37 table 17. tfbga48 6x8mm - 6x8 ball array, 0.8mm pitch, package mechanical data . . . . . . . . . . 38 table 18. ordering information scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 19. top boot block addresses, m29w320dt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 20. bottom boot block addresses, m29w320db . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 21. query structure overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 22. cfi query identification string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 23. cfi query system interface information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 table 24. device geometry definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 table 25. primary algorithm-specific extended query table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 table 26. security code area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 27. programmer technique bus operations, byte = v ih or v il . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 table 28. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
m29w320dt, m29w320db list of figures 5/56 list of figures figure 1. logic diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 figure 2. tsop connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 3. tfbga48 connections (top view through package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 4. block addresses (x8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 5. block addresses (x16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 6. data polling flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 figure 7. data toggle flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 8. ac measurement i/o waveform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 0 figure 9. read mode ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 10. write ac waveforms, write enable controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 figure 11. write ac waveforms, chip enable controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 figure 12. reset/block temporary unprotect ac waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 13. accelerated program timing waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 14. tsop48 lead plastic thin small outline, 12x20 mm, top view package outline . . . . . . 37 figure 15. tfbga48 6x8mm - 6x8 ball array, 0.8mm pitch, bottom view package outline . . . . . . . 38 figure 16. programmer equipment block protect flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 figure 17. programmer equipment chip unprotect flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 figure 18. in-system equipment block protect flowchart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 figure 19. in-system equipment chip unprotect flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
summary description m29w320dt, m29w320db 6/56 1 summary description the m29w320d is a 32 mbit (4mb x8 or 2mb x16) non-volatile memory that can be read, erased and reprogrammed. these operations can be performed using a single low voltage (2.7 to 3.6v) supply. on power-up the memory defaults to its read mode where it can be read in the same way as a rom or eprom. the memory is divided into blocks that can be erased independently so it is possible to preserve valid data while old data is erased. each block can be protected independently to prevent accidental program or erase commands from modifying the memory. program and erase commands are written to the command interface of the memory. an on-chip program/erase controller simplifies the process of programming or erasing the memory by taking care of all of the special operations that are required to update the memory contents. the end of a program or erase operation can be detected and any error conditions identified. the command set required to cont rol the memory is consistent with jedec standards. the blocks in the memory are asymmetrically arranged, see figure 4 and figure 5 , ta b l e 1 9 and ta b l e 2 0 . the first or last 64 kbytes have been divided into four additional blocks. the 16 kbyte boot block can be used for small initialization code to start the microprocessor, the two 8 kbyte parameter blocks can be used for parameter storage and the remaining 32 kbyte is a small main block where the application may be stored. chip enable, output enable and write enable signals control the bus operation of the memory. they allow simple connection to most microprocessors, often without additional logic. the memory is offered in tsop48 (12 x 20mm), and tfbga48 (6x8mm, 0.8mm pitch) packages. in order to meet environmental requirements, numonyx offers the m29w320d in ecopack ? packages. ecopack packages are lead-free. the category of second level interconnect is marked on the package and on the inner box label, in compliance with jedec standard jesd97. the maximum ratings related to soldering conditions are also marked on the inner box label. the memory is supplied with all the bits erased (set to 1).
m29w320dt, m29w320db summary description 7/56 figure 1. logic diagram table 1. signal names a0-a20 address inputs dq0-dq7 data inputs/outputs dq8-dq14 data inputs/outputs dq15a?1 data input/output or address input e chip enable g output enable w write enable rp reset/block temporary unprotect rb ready/busy output byte byte/word organization select v cc supply voltage v pp /wp v pp /write protect v ss ground nc not connected internally ai90189b 21 a0-a20 w dq0-dq14 v cc m29w320dt m29w320db e v ss 15 g rp dq15a?1 rb v pp /wp byte
summary description m29w320dt, m29w320db 8/56 figure 2. tsop connections dq3 dq9 dq2 a6 dq0 w a3 rb dq6 a8 a9 dq13 a17 a10 dq14 a2 dq12 dq10 dq15a?1 v cc dq4 dq5 a7 dq7 v pp /wp nc ai90190 m29w320dt m29w320db 12 1 13 24 25 36 37 48 dq8 a20 a19 a1 a18 a4 a5 dq1 dq11 g a12 a13 a16 a11 byte a15 a14 v ss e a0 rp v ss
m29w320dt, m29w320db summary description 9/56 figure 3. tfbga48 connections (top view through package) 6 5 4 3 2 1 v ss a15 a14 a12 a13 dq3 dq11 dq10 a18 v pp / wp rb dq1 dq9 dq8 dq0 a6 a17 a7 g e a0 a4 a3 dq2 dq6 dq13 dq14 a10 a8 a9 dq4 v cc dq12 dq5 a19 nc rp w a11 dq7 a1 a2 v ss a5 a20 a16 byte c b a e d f g h dq15 a?1 ai08084
summary description m29w320dt, m29w320db 10/56 figure 4. block addresses (x8) 1. also see appendix a: block addresses , table 19 and table 20 for a full listing of the block addresses. ai90192 16 kbyte 3fffffh 3fc000h 64 kbyte 01ffffh 010000h 64 kbyte 00ffffh 000000h m29w320dt top boot block addresses (x8) 32 kbyte 3f7fffh 3f0000h 64 kbyte 3e0000h 3effffh total of 63 64 kbyte blocks 16 kbyte 3fffffh 3f0000h 64 kbyte 64 kbyte 003fffh 000000h m29w320db bottom boot block addresses (x8) 32 kbyte 3effffh 01ffffh 64 kbyte 3e0000h 010000h total of 63 64 kbyte blocks 00ffffh 008000h 8 kbyte 8 kbyte 3fbfffh 3fa000h 3f9fffh 3f8000h 8 kbyte 8 kbyte 007fffh 006000h 005fffh 004000h
m29w320dt, m29w320db summary description 11/56 figure 5. block addresses (x16) 1. also see appendix appendix a: bloc k addresses , table 19 and table 20 for a full listing of the block addresses. ai90193 8 kword 1fffffh 1fe000h 32 kword 00ffffh 008000h 32 kword 007fffh 000000h m29w320dt top boot block addresses (x16) 16 kword 1fbfffh 1f8000h 32 kword 1f0000h 1f7fffh total of 63 32 kword blocks 8 kword 1fffffh 1f8000h 32 kword 32 kword 001fffh 000000h m29w320db bottom boot block addresses (x16) 16 kword 1f7fffh 00ffffh 32 kword 1f0000h 008000h total of 63 32 kword blocks 007fffh 004000h 4 kword 4 kword 1fdfffh 1fd000h 1fcfffh 1fc000h 4 kword 4 kword 003fffh 003000h 002fffh 002000h
signal descriptions m29w320dt, m29w320db 12/56 2 signal descriptions see figure 1: logic diagram , and table 1: signal names , for a brief overview of the signals connected to this device. 2.1 address inputs (a0-a20) the address inputs select the cells in the memory array to access during bus read operations. during bus write operations they control the commands sent to the command interface of the internal state machine. 2.2 data inputs/outputs (dq0-dq7) the data i/o outputs the data stored at the selected address during a bus read operation. during bus write operations they represent the commands sent to the command interface of the internal state machine. 2.3 data inputs/outputs (dq8-dq14) the data i/o outputs the data stored at the selected address during a bus read operation when byte is high, v ih . when byte is low, v il , these pins are not used and are high impedance. during bus write operations the command register does not use these bits. when reading the status register these bits should be ignored. 2.4 data input/output or address input (dq15a?1) when byte is high, v ih , this pin behaves as a data input/output pin (as dq8-dq14). when byte is low, v il , this pin behaves as an address pin; dq15a?1 low will select the lsb of the word on the other addresses, dq15a?1 high will select the msb. throughout the text consider references to the data input/output to include this pin when byte is high and references to the address inputs to include this pin when byte is low except when stated explicitly otherwise. 2.5 chip enable (e ) the chip enable, e , activates the memory, allowing bus read and bus write operations to be performed. when chip enable is high, v ih , all other pins are ignored. 2.6 output enable (g ) the output enable, g , controls the bus read operation of the memory.
m29w320dt, m29w320db signal descriptions 13/56 2.7 write enable (w ) the write enable, w , controls the bus write operation of the memory?s command interface. 2.8 v pp/ write protect (v pp /wp ) the v pp /write protect pin provides two functions. the v pp function allows the memory to use an external high voltage power supply to reduce the time required for unlock bypass program operations. the write protect function provides a hardware method of protecting the 16 kbyte boot block. the v pp /write protect pin must not be left floating or unconnected. when v pp /write protect is low, v il , the memory protects the 16 kbyte boot block; program and erase operations in this block are ignored while v pp /write protect is low. when v pp /write protect is high, v ih , the memory reverts to the previous protection status of the 16 kbyte boot block. program and erase operations can now modify the data in the 16 kbyte boot block unless the block is protected using block protection. when v pp /write protect is raised to v pp the memory automatically enters the unlock bypass mode. when v pp /write protect returns to v ih or v il normal operation resumes. during unlock bypass program operations the memory draws i pp from the pin to supply the programming circuits. see the description of the unlock bypass command in the command interface section. the transitions from v ih to v pp and from v pp to v ih must be slower than t vhvpp , see figure 13 . never raise v pp /write protect to v pp from any mode except read mode, otherwise the memory may be left in an indeterminate state. a 0.1f capacitor should be connected between the v pp /write protect pin and the v ss ground pin to decouple the current surges from the power supply. the pcb track widths must be sufficient to carry the currents required during unlock bypass program, i pp . 2.9 reset/block temporary unprotect (rp ) the reset/block temporary unprotect pin can be used to apply a hardware reset to the memory or to temporarily unprotect al l blocks that have been protected. note that if v pp /wp is at v il , then the 16 kbyte outermost boot block will remain protect even if rp is at v id . a hardware reset is achieved by holding reset/block temporary unprotect low, v il , for at least t plpx . after reset/block temporary unprotect goes high, v ih , the memory will be ready for bus read and bus write operations after t phel or t rhel , whichever occurs last. see the ready/busy output section, ta bl e 1 5 and figure 12 , for more details. holding rp at v id will temporarily unprotect the protec ted blocks in the memory. program and erase operations on all blocks will be possible. the transition from v ih to v id must be slower than t phphh .
signal descriptions m29w320dt, m29w320db 14/56 2.10 ready/busy output (rb ) the ready/busy pin is an open-drain output that can be used to identify when the device is performing a program or erase operation. during program or erase operations ready/busy is low, v ol . ready/busy is high-impedance during read mode, auto select mode and erase suspend mode. note that if v pp /wp is at v il , then the 16 kbyte outermost boot block will remain protect even if rp is at v id . after a hardware reset, bus read and bus write operations cannot begin until ready/busy becomes high-impedance. see ta bl e 1 5 and figure 12 . the use of an open-drain output allows the ready/busy pins from several memories to be connected to a single pull-up resistor. a low will then indicate that one, or more, of the memories is busy. 2.11 byte/word organization select (byte ) the byte/word organization select pin is used to switch between the x8 and x16 bus modes of the memory. when byte/word organization select is low, v il , the memory is in x8 mode, when it is high, v ih , the memory is in x16 mode. 2.12 v cc supply voltage v cc provides the power supply for all operations (read, program and erase). the command interface is disabled when the v cc supply voltage is less than the lockout voltage, v lko . this prevents bus write operations from accidentally damaging the data during power up, power down and power surges. if the program/erase controller is programming or erasing during this time then the operation aborts and the memory contents being altered will be invalid. a 0.1f capacitor should be connected between the v cc supply voltage pin and the v ss ground pin to decouple the current surges from the power supply. the pcb track widths must be sufficient to carry the currents required during program and erase operations, i cc3 . 2.13 v ss ground v ss is the reference for all voltage measurements.
m29w320dt, m29w320db bus operations 15/56 3 bus operations there are five standard bus operations that control the device. these are bus read, bus write, output disable, standby and automatic standby. see ta bl e 2 and ta b l e 3 , bus operations, for a summary. typically glitches of less than 5ns on chip enable or write enable are ignored by the memory and do not affect bus operations. 3.1 bus read bus read operations read from the memory cells, or specific registers in the command interface. a valid bus read operation involves setting the desired address on the address inputs, applying a low signal, v il , to chip enable and output enable and keeping write enable high, v ih . the data inputs /outputs will output the value, see figure 9: read mode ac waveforms , and table 12: read ac characteristics , for details of when the output becomes valid. 3.2 bus write bus write operations write to the command interface. a valid bus write operation begins by setting the desired address on the address inputs. the address inputs are latched by the command interface on the falling edge of chip enable or write enable, whichever occurs last. the data inputs/outputs are latched by the command interface on the rising edge of chip enable or write enable, whichever occurs first. output enable must remain high, v ih , during the whole bus write operation. see figure 10 and figure 11 , write ac waveforms, and ta b l e 1 3 and ta bl e 1 4 , write ac characteristics, for details of the timing requirements. 3.3 output disable the data inputs/outputs are in the high impedance state when output enable is high, v ih . 3.4 standby when chip enable is high, v ih , the memory enters standby mode and the data inputs/outputs pins are placed in the high-impedance state. to reduce the supply current to the standby supply current, i cc2 , chip enable should be held within v cc 0.2v. for the standby current level see table 11: dc characteristics . during program or erase oper ations the memory will contin ue to use the program/erase supply current, i cc3 , for program or erase operations until the operation completes. 3.5 automatic standby if cmos levels (v cc 0.2v) are used to drive the bus and the bus is inactive for 300ns or more the memory enters automatic standby where the internal supply current is reduced to the standby supply current, i cc2 . the data inputs/outputs will still output data if a bus read operation is in progress.
bus operations m29w320dt, m29w320db 16/56 3.6 special bus operations additional bus operations can be performed to read the electronic signature and also to apply and remove block protection. these bus operations are intended for use by programming equipment and are not usually used in applications. they require v id to be applied to some pins. 3.6.1 electronic signature the memory has two codes, the manufacturer code and the device code, that can be read to identify the memory. these codes can be read by applying the signals listed in ta b l e 2 and ta b l e 3 , bus operations. 3.6.2 block protect and chip unprotect each block can be separately protected against accidental program or erase. the whole chip can be unprotected to allow the data inside the blocks to be changed. block protect and chip unprotect operations are described in appendix c: block protection . table 2. bus operations, byte = v il (1) operation e g w address inputs dq15a?1, a0-a20 data inputs/outputs dq14-dq8 dq7-dq0 bus read v il v il v ih cell address hi-z data output bus write v il v ih v il command address hi-z data input output disable x v ih v ih x hi-z hi-z standby v ih x x x hi-z hi-z read manufacturer code v il v il v ih a0 = v il , a1 = v il , a9 = v id , others v il or v ih hi-z 20h read device code v il v il v ih a0 = v ih , a1 = v il , a9 = v id , others v il or v ih hi-z cah (m29w320dt) cbh (m29w320db) 1. x = v il or v ih . table 3. bus operations, byte = v ih (1) operation e g w address inputs a0-a20 data inputs/outputs dq15a?1, dq14-dq0 bus read v il v il v ih cell address data output bus write v il v ih v il command address data input output disable x v ih v ih xhi-z standby v ih xxx hi-z read manufacturer code v il v il v ih a0 = v il , a1 = v il , a9 = v id , others v il or v ih 0020h read device code v il v il v ih a0 = v ih , a1 = v il , a9 = v id , others v il or v ih 22cah (m29w320dt) 22cbh (m29w320db) 1. x = v il or v ih .
m29w320dt, m29w320db command interface 17/56 4 command interface all bus write operations to the memory are interpreted by the command interface. commands consist of one or more sequential bus write operations. failure to observe a valid sequence of bus write operations will resu lt in the memory retu rning to read mode. the long command sequences are imposed to maximize data security. the address used for the commands changes depending on whether the memory is in 16- bit or 8-bit mode. see either ta bl e 4 , or ta b l e 5 , depending on the configuration that is being used, for a summary of the commands. 4.1 read/reset command the read/reset command returns the memory to its read mode where it behaves like a rom or eprom, unless otherwise stated. it also resets the errors in the status register. either one or three bus write operations can be used to issue the read/reset command. the read/reset command can be issued, between bus write cycles before the start of a program or erase operation, to return the device to read mode. once the program or erase operation has started the read/reset command is no longer accepted. the read/reset command will not abort an erase operatio n when issued while in erase suspend. 4.2 auto select command the auto select command is used to read the manufacturer code, the device code and the block protection status. three consecutive bus write operations are required to issue the auto select command. once the auto select command is issued the memory remains in auto select mode until a read/reset command is issued. read cfi query and read/reset commands are accepted in auto select mode, all other commands are ignored. from the auto select mode the manufacturer code can be read using a bus read operation with a0 = v il and a1 = v il . the other address bits may be set to either v il or v ih . the manufacturer code for numonyx is 0020h. the device code can be read using a bus read operation with a0 = v ih and a1 = v il . the other address bits may be set to either v il or v ih . the device code for the m29w320dt is 22cah and for the m29w320db is 22cbh. the block protection status of each block can be read using a bus read operation with a0 = v il , a1 = v ih , and a12-a20 specifying the address of the block. the other address bits may be set to either v il or v ih . if the addressed block is protected then 01h is output on data inputs/outputs dq0-dq7, otherwise 00h is output.
command interface m29w320dt, m29w320db 18/56 4.3 read cfi query command the read cfi query command is used to read data from the common flash interface (cfi) memory area. this command is valid when the device is in the read array mode, or when the device is in autoselected mode. one bus write cycle is required to issue the read cfi query command. once the command is issued subsequent bus read operations read from the common flash interface memory area. the read/reset command must be issued to return the device to the previous mode (the read array mode or autoselected mode). a second read/reset command would be needed if the device is to be put in the read array mode from autoselected mode. see appendix b: common flash interface (cfi) , ta b l e 2 1 , ta bl e 2 2 , ta b l e 2 3 , ta bl e 2 4 , ta bl e 2 5 and ta bl e 2 6 for details on the information contained in the common flash interface (cfi) memory area. 4.4 program command the program command can be used to program a value to one address in the memory array at a time. the command requires four bus write operations, the final write operation latches the address and data in the internal state machine and starts the program/erase controller. if the address falls in a protected block then the program command is ignored, the data remains unchanged. the status register is ne ver read and no error condition is given. during the program operation the memory will i gnore all commands. it is not possible to issue any command to abort or pause the operation. typical program times are given in ta bl e 6 . bus read operations during the program operation will ou tput the status register on the data inputs/outputs. see the section on the status register for more details. after the program operat ion has completed the memory will re turn to the read mode, unless an error has occurred. when an error occurs the memory will continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. note that the program command cannot change a bit set at ?0? back to ?1?. one of the erase commands must be used to set all the bits in a block or in the whole me mory from ?0? to ?1?. 4.5 unlock bypass command the unlock bypass command is used in conjunction with the unlock bypass program command to program the memory. when the cycle time to the device is long (as with some eprom programmers) considerable time saving can be made by using these commands. three bus write operations are required to issue the unlock bypass command. once the unlock bypass command has been is sued the memory will only accept the unlock bypass program command and the unlock bypass reset command. the memory can be read as if in read mode. the memory offers accelerated program operations through the v pp /write protect pin. when the system asserts v pp on the v pp /write protect pin, the memory automatically enters the unlock bypass mo de. the system may then write the two-cycle unlock bypass
m29w320dt, m29w320db command interface 19/56 program command sequence. the memory uses the higher voltage on the v pp /write protect pin, to accelerate the unlock bypass program operation. never raise v pp /write protect to v pp from any mode except read mode, otherwise the memory may be left in an indeterminate state. 4.6 unlock bypass program command the unlock bypass program command can be used to program one address in the memory array at a time. the command requires two bus write operations, the final write operation latches the address and data in the internal state machine and starts the program/erase controller. the program operation using the unlock bypass program command behaves identically to the program operation using the program command. the operation cannot be aborted, the status register is read and protected blocks cannot be programmed. errors must be reset using the read/reset command, which leaves the device in unlock bypass mode. see the program command for details on the behavior. 4.7 unlock bypass reset command the unlock bypass reset command can be used to return to read/reset mode from unlock bypass mode. two bus write operations are required to issue the unlock bypass reset command. read/reset command does not exit from unlock bypass mode. 4.8 chip erase command the chip erase command can be used to erase the entire chip. six bus write operations are required to issue the chip erase command and start the program/erase controller. if any blocks are protected then these are ignored and all the other blocks are erased. if all of the blocks are protected the chip erase operation appears to start but will terminate within about 100s, leaving the data unchanged. no error condition is given when protected blocks are ignored. during the erase operation the memory will ignore all commands, including the erase suspend command. it is not possible to issue any command to abort the operation. typical chip erase times are given in ta bl e 6 . all bus read operations during the chip erase operation will output the status register on the data input s/outputs. see the section on the status register for more details. after the chip erase operation has complet ed the memory will return to the read mode, unless an error has occurred. when an error oc curs the memory will co ntinue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. the chip erase command sets all of the bits in unprotected blocks of the memory to ?1?. all previous data is lost.
command interface m29w320dt, m29w320db 20/56 4.9 block erase command the block erase command can be used to erase a list of one or more blocks. six bus write operations are required to select the first block in the list. each additional block in the list can be selected by repeating the sixth bus write operation using the address of the additional block. the block erase operation starts the program/erase controller about 50s after the last bus write operation. once the program/erase controller starts it is not possible to select any more blocks. each additional block must therefore be selected within 50s of the last block. the 50s timer restarts when an additional block is selected. the status register can be read after the sixth bus write operation. see the status register section for details on how to identify if the program/erase controller has started the block erase operation. if any selected blocks are protected then these are ignored and all the other selected blocks are erased. if all of the selected blocks are protected the block erase operation appears to start but will terminate wit hin about 100s, leaving the data un changed. no erro r condition is given when protected blocks are ignored. during the block erase operat ion the memory will ignore a ll commands except the erase suspend command. typical block erase times are given in ta bl e 6 . all bus read operations during the block erase operation will output the status register on t he data inputs/outputs. see the section on the status register for more details. after the block erase operation has complete d the memory will return to the read mode, unless an error has occurred. when an error oc curs the memory will co ntinue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. the block erase command sets all of the bits in the unprotected selected blocks to ?1?. all previous data in the selected blocks is lost. 4.10 erase suspend command the erase suspend command may be used to temporarily suspend a block erase operation and return the memory to read mode. the command requires one bus write operation. the program/erase controller will suspend within the erase suspend latency time (refer to ta bl e 6 for value) of the erase suspend command being issued. once the program/erase controller has stopped the me mory will be set to read mo de and the erase will be suspended. if the erase suspend command is issued during the period when the memory is waiting for an additional block (before the program/erase controller starts) then the erase is suspended immediately and will start immedi ately when the erase resume command is issued. it is not possible to select any furt her blocks to erase after the erase resume. during erase suspend it is possible to read and program cells in blocks that are not being erased; both read and program operations behave as normal on these blocks. if any attempt is made to program in a protected block or in the suspended block then the program command is ignored and the data remains unchanged. the status register is not read and no error condition is given. reading from bloc ks that are being erased will output the status register. it is also possible to issue the auto select, read cfi query and unlock bypass commands during an erase suspend. the read/reset command must be issued to return the device to read array mode before the resume command will be accepted.
m29w320dt, m29w320db command interface 21/56 4.11 erase resume command the erase resume command must be used to restart the program/erase controller after an erase suspend. the device must be in read array mode before the resume command will be accepted. an erase can be suspended and resumed more than once. 4.12 block protect and chip unprotect commands each block can be separately protected against accidental program or erase. the whole chip can be unprotected to allow the data inside the blocks to be changed. block protect and chip unprotect operations are described in appendix c: block protection .
command interface m29w320dt, m29w320db 22/56 table 4. commands, 16-bit mode, byte = v ih (1)(2) command length bus write operations 1st 2nd 3rd 4th 5th 6th addr data addr data addr data addr data addr data addr data read/reset (3) 1x f0 3 555 aa 2aa 55 x f0 auto select (4) 3 555 aa 2aa 55 555 90 program (5) 4 555 aa 2aa 55 555 a0 pa pd unlock bypass (6) 3 555 aa 2aa 55 555 20 unlock bypass program (5) 2x a0papd unlock bypass reset (7) 2x 90 x 00 chip erase (5) 6 555 aa 2aa 55 555 80 555 aa 2aa 55 555 10 block erase (5) 6+ 555 aa 2aa 55 555 80 555 aa 2aa 55 ba 30 erase suspend (8) 1x b0 erase resume (9) 1x 30 read cfi query (10) 155 98 1. x don?t care, pa program address, pd program data, ba an y address in the block. all values in the table are in hexadecimal. 2. the command interface only uses a?1, a0-a10 and dq0-dq 7 to verify the commands; a11-a20, dq8-dq14 and dq15 are don?t care. dq15a?1 is a?1 when byte is v il or dq15 when byte is v ih . 3. after a read/reset command, read the memory as normal until another command is issued. read/reset command is ignored during algorithm execution. 4. after an auto select command, read manufacturer id, device id or bl ock protection status. 5. after program, unlock bypass program, chip erase, block erase commands read the status register until the program/erase controller completes and the memory return s to read mode. add additional blocks duri ng block erase command with additional bus write operations until timeout bit is set. 6. after the unlock bypass command issue unlock by pass program or unlock bypass reset commands. 7. after the unlock bypass reset command read the memo ry as normal until another command is issued. 8. after the erase suspend command read non- erasing memory blocks as normal, issue auto select and program commands on non-erasing blocks as normal. 9. after the erase resume command the suspended erase oper ation resumes, read the status register until the program/erase controller completes and the memory returns to read mode. 10. cfi query command is valid when devic e is ready to read array data or w hen device is in autoselected mode.
m29w320dt, m29w320db command interface 23/56 table 5. commands, 8-bit mode, byte = v il (1)(2) command length bus write operations 1st 2nd 3rd 4th 5th 6th addr data addr data addr data addr data addr data addr data read/reset (3) 1x f0 3 aaa aa 555 55 x f0 auto select (4) 3 aaa aa 555 55 aaa 90 program (5) 4 aaa aa 555 55 aaa a0 pa pd unlock bypass (6) 3 aaa aa 555 55 aaa 20 unlock bypass program (5) 2 x a0 pa pd unlock bypass reset (7) 2x 90 x 00 chip erase (5) 6 aaa aa 555 55 aaa 80 aaa aa 555 55 aaa 10 block erase (5) 6+ aaa aa 555 55 aaa 80 aaa aa 555 55 ba 30 erase suspend (8) 1x b0 erase resume (9) 1x 30 read cfi query (10) 1aa 98 1. x don?t care, pa program address, pd program data, ba an y address in the block. all values in the table are in hexadecimal. 2. the command interface only uses a?1, a0-a10 and dq0-dq 7 to verify the commands; a11-a20, dq8-dq14 and dq15 are don?t care. dq15a?1 is a?1 when byte is v il or dq15 when byte is v ih . 3. after a read/reset command, read the memory as normal until another command is issued. read/reset command is ignored during algorithm execution. 4. after an auto select command, read manufacturer id, device id or bl ock protection status. 5. after a program, unlock bypass program, chip erase, block erase command read the status register until the program/erase controller completes and the memory return s to read mode. add additional blocks duri ng block erase command with additional bus write operations until timeout bit is set. 6. after the unlock bypass command issue unlock by pass program or unlock bypass reset commands. 7. after the unlock bypass reset command read the memo ry as normal until another command is issued. 8. after the erase suspend command read non- erasing memory blocks as normal, issue auto select and program commands on non-erasing blocks as normal. 9. after the erase resume command the suspended erase oper ation resumes, read the status register until the program/erase controller completes and the memory returns to read mode. 10. the cfi query command is valid when device is ready to read array data or when devic e is in autoselected mode.
command interface m29w320dt, m29w320db 24/56 table 6. program, erase times and program, erase endurance cycles parameter min typ (1)(2) max (2) unit chip erase 40 200 (3) s block erase (64 kbytes) 0.8 6 (4) s erase suspend latency time 15 25 (4) s program (byte or word) 10 200 (3) s accelerated program (byte or word) 8 150 (3) s chip program (byte by byte) 40 200 (3) s chip program (word by word) 20 100 (3) s program/erase cycles (per block) 100,000 cycles data retention 20 years 1. typical values measured at room temperature and nominal voltages. 2. sampled, but not 100% tested. 3. maximum value measured at worst case conditions for both temperature and v cc after 100,00 program/erase cycles. 4. maximum value measured at worst case conditions for both temperature and v cc .
m29w320dt, m29w320db status register 25/56 5 status register bus read operations from any address always read the status register during program and erase operations. it is also read during erase suspend when an address within a block being erased is accessed. the bits in the status register are summarized in table 7: status register bits . 5.1 data polling bit (dq7) the data polling bit can be used to identi fy whether the program/erase controller has successfully completed its operation or if it has responded to an erase suspend. the data polling bit is output on dq7 when the status register is read. during program operations the data polling bi t outputs the compleme nt of the bit being programmed to dq7. after successful completion of the program operation the memory returns to read mode and bus read operations from the address just programmed output dq7, not its complement. during erase operations the data polling bit outp uts ?0?, the complement of the erased state of dq7. after successful completion of the erase operation the memory returns to read mode. in erase suspend mode the da ta polling bit will output a ?1? during a bus read operation within a block being erased. the data polling bit will change from a ?0? to a ?1? when the program/erase controller has suspended the erase operation. figure 6: data polling flowchart , gives an example of how to use the data polling bit. a valid address is the address being programmed or an address within the block being erased. 5.2 toggle bit (dq6) the toggle bit can be used to identify whether the program/erase controller has successfully completed its operation or if it has responded to an erase suspend. the toggle bit is output on dq6 when the status register is read. during program and erase operations the toggle bit changes from ?0? to ?1? to ?0?, etc., with successive bus read operations at any addres s. after successful completion of the operation the memory returns to read mode. during erase suspend mo de the toggle bit will output when addressing a cell within a block being erased. the toggle bit will stop togglin g when the program/erase controller has suspended the erase operation. if any attempt is made to erase a protected block, the operation is aborted, no error is signalled and dq6 toggles for approximately 100s. if any attempt is made to program a protected block or a suspended block, the operation is aborted, no error is signalled and dq6 toggles for approximately 1s. figure 7: data toggle flowchart , gives an example of how to use the data toggle bit.
status register m29w320dt, m29w320db 26/56 5.3 error bit (dq5) the error bit can be used to identify errors detected by the program/erase controller. the error bit is set to ?1? when a program, block erase or chip erase operation fails to write the correct data to the memory. if the error bit is set a read/reset command must be issued before other commands are issued. the error bit is output on dq5 when the status register is read. note that the program command cannot change a bit set to ?0? back to ?1? and attempting to do so will set dq5 to ?1?. a bus read operation to that address will show the bit is still ?0?. one of the erase commands must be used to set all the bits in a block or in the whole memory from ?0? to ?1?. 5.4 erase timer bit (dq3) the erase timer bit can be used to identify the start of program/erase controller operation during a block erase command. once the program/erase controller starts erasing the erase timer bit is set to ?1?. before the program/erase controller starts the erase timer bit is set to ?0? and additional blocks to be eras ed may be written to the command interface. the erase timer bit is output on dq3 when the status register is read. 5.5 alternative toggle bit (dq2) the alternative toggle bit can be used to monitor the program/erase controller during erase operations. the alternative toggle bit is output on dq2 when the status register is read. during chip erase and block erase operations the toggle bit changes from ?0? to ?1? to ?0?, etc., with successive bus read operations from addresses within the blocks being erased. a protected block is treated the same as a block not being erased. once the operation completes the memory returns to read mode. during erase suspend the alternative toggle bi t changes from ?0? to ?1? to ?0?, etc. with successive bus read operations from addresses within the blocks being erased. bus read operations to addresses within blocks not be ing erased will output the me mory cell data as if in read mode. after an erase operation that causes the error bit to be set the alternative toggle bit can be used to identify which block or blocks have caused the error. the alternative toggle bit changes from ?0? to ?1? to ?0 ?, etc. with successive bus read operations from addresses within blocks that have not erased correctly. the alternative toggle bit does not change if the addressed block has erased correctly.
m29w320dt, m29w320db status register 27/56 figure 6. data polling flowchart table 7. status register bits (1) operation address dq7 dq6 dq5 dq3 dq2 rb program any address dq7 toggle0??0 program during erase suspend any address dq7 toggle0??0 program error any address dq7 toggle1??0 chip erase any address 0 toggle 0 1 toggle 0 block erase before timeout erasing block 0 toggle 0 0 toggle 0 non-erasing block 0 toggle 0 0 no toggle 0 block erase erasing block 0 toggle 0 1 toggle 0 non-erasing block 0 toggle 0 1 no toggle 0 erase suspend erasing block 1 no toggle 0 ? toggle 1 non-erasing block data read as normal 1 erase error good block address 0 toggle 1 1 no toggle 0 faulty block address 0 toggle 1 1 toggle 0 1. unspecified data bi ts should be ignored. read dq5 & dq7 at valid address start read dq7 at valid address fail pass ai90194 dq7 = data yes no yes no dq5 = 1 dq7 = data yes no
status register m29w320dt, m29w320db 28/56 figure 7. data toggle flowchart read dq6 start read dq6 twice fail pass ai01370c dq6 = toggle no no yes yes dq5 = 1 no yes dq6 = toggle read dq5 & dq6
m29w320dt, m29w320db maximum rating 29/56 6 maximum rating stressing the device above the rating listed in the absolute maximum ratings table may cause permanent damage to the device. exposure to absolute maximum rating conditions for extended periods may affect device relia bility. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not implied. refer also to the numonyx sure program and other relevant quality documents. table 8. absolute maximum ratings symbol parameter min max unit t bias temperature under bias ?50 125 c t stg storage temperature ?65 150 c v io input or output voltage (1)(2) 1. minimum voltage may undershoot to ?2v during trans ition and for less than 20ns during transitions. 2. maximum voltage may overshoot to v cc +2v during transition and for less than 20ns during transitions. ?0.6 v cc +0.6 v v cc supply voltage ?0.6 4 v v id identification voltage ?0.6 13.5 v v pp program voltage ?0.6 13.5 v
dc and ac parameters m29w320dt, m29w320db 30/56 7 dc and ac parameters this section summarizes the operating measurement conditions, and the dc and ac characteristics of the device. the parameters in the dc and ac characteristics tables that follow, are derived from tests performed under the measurement conditions summarized in table 9: operating and ac measurement conditions . designers should check that the operating conditions in their circuit match the operating conditions when relying on the quoted parameters. figure 8. ac measurement i/o waveform table 9. operating and ac measurement conditions parameter m29w320d unit 70 90 min max min max v cc supply voltage 3.0 3.6 2.7 3.6 v ambient operating temperature ?40 85 ?40 85 c load capacitance (c l )3030pf input rise and fall times 10 10 ns input pulse voltages 0 to v cc 0 to v cc v input and output timing ref. voltages v cc /2 v cc /2 v ai90196 v cc 0v v cc /2
m29w320dt, m29w320db dc and ac parameters 31/56 figure 1. ac measurement load circuit table 10. device capacitance (1) 1. sampled only, not 100% tested. symbol parameter test condition min max unit c in input capacitance v in = 0v 6 pf c out output capacitance v out = 0v 12 pf ai90197 c l c l includes jig capacitance device under test 25k v cc 25k v cc 0.1f v pp 0.1f
dc and ac parameters m29w320dt, m29w320db 32/56 table 11. dc characteristics symbol parameter test condition min typ. max unit i li input leakage current 0v v in v cc 1 a i lo output leakage current 0v v out v cc 1 a i cc1 supply current (read) e = v il , g = v ih , f = 6mhz 510ma i cc2 supply current (standby) e = v cc 0.2v, rp = v cc 0.2v 35 100 a i cc3 (1) supply current (program/erase) program/eras e controller active v pp /wp = v il or v ih 20 ma v pp /wp = v pp 20 ma v il input low voltage ?0.5 0.8 v v ih input high voltage 0.7v cc v cc +0.3 v v pp voltage for v pp /wp program acceleration v cc = 3.0v 10% 11.5 12.5 v i pp current for v pp /wp program acceleration v cc = 3.0v 10% 10 ma v ol output low voltage i ol = 1.8ma 0.45 v v oh output high voltage i oh = ?100 av cc ?0.4 v v id identification voltage 11.5 12.5 v i id identification current a9 = v id 100 a v lko program/erase lockout supply voltage 1.8 2.3 v 1. sampled only, not 100% tested.
m29w320dt, m29w320db dc and ac parameters 33/56 figure 9. read mode ac waveforms ai90198 tavav tavqv taxqx telqx tehqz tglqv tglqx tghqx valid a0-a20/ a?1 g dq0-dq7/ dq8-dq15 e telqv tehqx tghqz valid tbhqv telbl/telbh tblqz byte table 12. read ac characteristics symbol alt parameter test condition m29w320d unit 70 90 t avav t rc address valid to ne xt address valid e = v il , g = v il min 70 90 ns t avqv t acc address valid to output valid e = v il , g = v il max 70 90 ns t elqx (1) t lz chip enable low to output transition g = v il min 0 0 ns t elqv t ce chip enable low to output valid g = v il max 70 90 ns t glqx (1) t olz output enable low to output tr a n s i t i o n e = v il min 0 0 ns t glqv t oe output enable low to output valid e = v il max 30 35 ns t ehqz (1) t hz chip enable high to output hi-z g = v il max 25 30 ns t ghqz (1) t df output enable high to output hi-z e = v il max 25 30 ns t ehqx t ghqx t axqx t oh chip enable, output enable or address transition to output transition min 0 0 ns t elbl t elbh t elfl t elfh chip enable to byte low or high max 5 5 ns t blqz t flqz byte low to output hi-z max 25 30 ns t bhqv t fhqv byte high to output valid max 30 40 ns 1. sampled only, not 100% tested.
dc and ac parameters m29w320dt, m29w320db 34/56 figure 10. write ac waveforms, write enable controlled ai90199 e g w a0-a20/ a?1 dq0-dq7/ dq8-dq15 valid valid v cc tvchel twheh twhwl telwl tavwl twhgl twlax twhdx tavav tdvwh twlwh tghwl rb twhrl table 13. write ac characteristics, write enable controlled symbol alt parameter m29w320d unit 70 90 t avav t wc address valid to next address valid min 70 90 ns t elwl t cs chip enable low to write enable low min 0 0 ns t wlwh t wp write enable low to write enable high min 45 50 ns t dvwh t ds input valid to write enable high min 45 50 ns t whdx t dh write enable high to input transition min 0 0 ns t wheh t ch write enable high to chip enable high min 0 0 ns t whwl t wph write enable high to write enable low min 30 30 ns t avwl t as address valid to write enable low min 0 0 ns t wlax t ah write enable low to address transition min 45 50 ns t ghwl output enable high to write enable low min 0 0 ns t whgl t oeh write enable high to output enable low min 0 0 ns t whrl (1) t busy program/erase valid to rb low max 30 35 ns t vchel t vcs v cc high to chip enable low min 50 50 s 1. sampled only, not 100% tested.
m29w320dt, m29w320db dc and ac parameters 35/56 figure 11. write ac waveforms, chip enable controlled ai90200 e g w a0-a20/ a?1 dq0-dq7/ dq8-dq15 valid valid v cc tvchwl tehwh tehel twlel tavel tehgl telax tehdx tavav tdveh teleh tghel rb tehrl table 14. write ac characteristics, chip enable controlled symbol alt parameter m29w320d unit 70 90 t avav t wc address valid to next address valid min 70 90 ns t wlel t ws write enable low to chip enable low min 0 0 ns t eleh t cp chip enable low to chip enable high min 45 50 ns t dveh t ds input valid to chip enable high min 45 50 ns t ehdx t dh chip enable high to input transition min 0 0 ns t ehwh t wh chip enable high to write enable high min 0 0 ns t ehel t cph chip enable high to chip enable low min 30 30 ns t avel t as address valid to chip enable low min 0 0 ns t elax t ah chip enable low to address transition min 45 50 ns t ghel output enable high chip enable low min 0 0 ns t ehgl t oeh chip enable high to output enable low min 0 0 ns t ehrl (1) t busy program/erase valid to rb low max 30 35 ns t vchwl t vcs v cc high to write enable low min 50 50 s 1. sampled only, not 100% tested.
dc and ac parameters m29w320dt, m29w320db 36/56 figure 12. reset/block temporary unprotect ac waveforms figure 13. accelerated program timing waveforms ai02931c rb w, rp tplpx tphwl, tphel, tphgl tplyh tphphh e, g trhwl, trhel, trhgl table 15. reset/block temporary unprotect ac characteristics symbol alt parameter m29w320d unit 70 90 t phwl (1) t phel t phgl (1) t rh rp high to write enable low, chip enable low, output enable low min 50 50 ns t rhwl (1) t rhel (1) t rhgl (1) t rb rb high to write enable low, chip enable low, output enable low min 0 0 ns t plpx t rp rp pulse width min 500 500 ns t plyh (1) t ready rp low to read mode max 25 25 s t phphh (1) t vidr rp rise time to v id min 500 500 ns t vhvpp (1) v pp rise and fall time min 250 250 ns 1. sampled only, not 100% tested. ai90202 v pp /wp v pp v il or v ih tvhvpp tvhvpp
m29w320dt, m29w320db package mechanical 37/56 8 package mechanical figure 14. tsop48 lead plastic thin small outline, 12x20 mm, top view package outline 1. drawing not to scale. tsop-g b e die c l a1 e1 e a a2 1 24 48 25 d1 l1 cp table 16. tsop48 lead plastic thin small outline, 12x20 mm, package mechanical data symbol millimeters inches typ min max typ min max a 1.200 0.0472 a1 0.100 0.050 0.150 0.0039 0.0020 0.0059 a2 1.000 0.950 1.050 0.0394 0.0374 0.0413 b 0.220 0.170 0.270 0.0087 0.0067 0.0106 c 0.100 0.210 0.0039 0.0083 cp 0.080 0.0031 d1 12.000 11.900 12.100 0.4724 0.4685 0.4764 e 20.000 19.800 20.200 0.7874 0.7795 0.7953 e1 18.400 18.300 18.500 0.7244 0.7205 0.7283 e 0.500 ? ? 0.0197 ? ? l 0.600 0.500 0.700 0.0236 0.0197 0.0276 l1 0.800 0.0315 a305305
package mechanical m29w320dt, m29w320db 38/56 figure 15. tfbga48 6x8mm - 6x8 ball array, 0.8mm pitch, bottom view package outline 1. drawing not to scale. e1 e d1 d e b a2 a1 a bga-z32 ddd fd fe sd se e ball "a1" table 17. tfbga48 6x8mm - 6x8 ball array, 0.8mm pitch, package mechanical data symbol millimeters inches typ min max typ min max a 1.200 0.0472 a1 0.260 0.0102 a2 0.900 0.0354 b 0.350 0.450 0.0138 0.0177 d 6.000 5.900 6.100 0.2362 0.2323 0.2402 d1 4.000 ? ? 0.1575 ? ? ddd 0.100 0.0039 e 8.000 7.900 8.100 0.3150 0.3110 0.3189 e1 5.600 ? ? 0.2205 ? ? e 0.800 ? ? 0.0315 ? ? fd 1.000 ? ? 0.0394 ? ? fe 1.200 ? ? 0.0472 ? ? sd 0.400 ? ? 0.0157 ? ? se 0.400 ? ? 0.0157 ? ?
m29w320dt, m29w320db part numbering 39/56 9 part numbering devices are shipped from the factory with the memory content bits erased to ?1?. for a list of available options (speed, package, etc...) or for further information on any aspect of this device, please contact the numonyx sales office nearest to you. table 18. ordering information scheme example: m29w320db 90 n 1 t device type m29 operating voltage w = v cc = 2.7 to 3.6v device function 320d = 32 mbit (x8/x16), non-uniform parameter blocks, boot block array matrix t = top boot b = bottom boot speed 70 = 70 ns 90 = 90 ns package n = tsop48: 12 x 20 mm ze = tfbga48: 6 x 8mm, 0.8mm pitch temperature range 1 = 0 to 70 c 6 = ?40 to 85 c option blank = standard packing t = tape & reel packing e = ecopack package, standard packing f = ecopack package, tape & reel packing
block addresses m29w320dt, m29w320db 40/56 appendix a block addresses table 19. top boot block addresses, m29w320dt # size (kbyte/kwor d) address range (x8) address range (x16) 66 16/8 3fc000h-3fff ffh 1fe000h-1fffffh 65 8/4 3fa000h-3fbfffh 1fd000h-1fdfffh 64 8/4 3f8000h-3f9ff fh 1fc000h-1fcfffh 63 32/16 3f0000h-3f7fffh 1f8000h-1fbfffh 62 64/32 3e0000h-3effff h 1f0000h-1f7fffh 61 64/32 3d0000h-3dffffh 1e8000h-1effffh 60 64/32 3c0000h-3cffff h 1e0000h-1e7fffh 59 64/32 3b0000h-3bff ffh 1d8000h-1dffffh 58 64/32 3a0000h-3affffh 1d0000h-1d7fffh 57 64/32 390000h-39ffffh 1c8000h-1cffffh 56 64/32 380000h-18ffffh 1c0000h-1c7fffh 55 64/32 370000h-37ffffh 1b8000h-1bffffh 54 64/32 360000h-36ffffh 1b0000h-1b7fffh 53 64/32 350000h-35ffffh 1a8000h-1affffh 52 64/32 340000h-34ffffh 1a0000h-1a7fffh 51 64/32 330000h-33ffffh 198000h-19ffffh 50 64/32 320000h-32ffffh 190000h-197fffh 49 64/32 310000h-31ffffh 188000h-18ffffh 48 64/32 300000h-30ffffh 180000h-187fffh 47 64/32 2f0000h-2fffffh 178000h-17ffffh 46 64/32 2e0000h-2eff ffh 170000h-177fffh 45 64/32 2d0000h-2dff ffh 168000h-16ffffh 44 64/32 2c0000h-2cff ffh 160000h-167fffh 43 64/32 2b0000h-2bff ffh 158000h-15ffffh 42 64/32 2a0000h-2aff ffh 150000h-157fffh 41 64/32 290000h-29ffffh 148000h-14ffffh 40 64/32 280000h-28ffffh 140000h-147fffh 39 64/32 270000h-27ffffh 138000h-13ffffh 38 64/32 260000h-26ffffh 130000h-137fffh 37 64/32 250000h-25ffffh 128000h-12ffffh 36 64/32 240000h-24ffffh 120000h-127fffh
m29w320dt, m29w320db block addresses 41/56 35 64/32 230000h-23ffffh 118000h-11ffffh 34 64/32 220000h-22ffffh 110000h-117fffh 33 64/32 210000h-21ffffh 108000h-10ffffh 32 64/32 200000h-20ffffh 100000h-107fffh 31 64/32 1f0000h-1fffffh 0f8000h-0fbfffh 30 64/32 1e0000h-1effff h 0f0000h-0f7fffh 29 64/32 1d0000h-1dffffh 0e8000h-0effffh 28 64/32 1c0000h-1cffff h 0e0000h-0e7fffh 27 64/32 1b0000h-1bff ffh 0d8000h-0dffffh 26 64/32 1a0000h-1affffh 0d0000h-0d7fffh 25 64/32 190000h-19ffffh 0c8000h-0cffffh 24 64/32 180000h-18ffffh 0c0000h-0c7fffh 23 64/32 170000h-17ffffh 0b8000h-0bffffh 22 64/32 160000h-16ffffh 0b0000h-0b7fffh 21 64/32 150000h-15ffffh 0a8000h-0affffh 20 64/32 140000h-14ffffh 0a0000h-0a7fffh 19 64/32 130000h-13ffffh 098000h-09ffffh 18 64/32 120000h-12ffffh 090000h-097fffh 17 64/32 110000h-11ffffh 088000h-08ffffh 16 64/32 100000h-10ffffh 080000h-087fffh 15 64/32 0f0000h-0fffffh 078000h-07ffffh 14 64/32 0e0000h-0eff ffh 070000h-077fffh 13 64/32 0d0000h-0dff ffh 068000h-06ffffh 12 64/32 0c0000h-0cff ffh 060000h-067fffh 11 64/32 0b0000h-0bff ffh 058000h-05ffffh 10 64/32 0a0000h-0aff ffh 050000h-057fffh 9 64/32 090000h-09ffffh 048000h-04ffffh 8 64/32 080000h-08ffffh 040000h-047fffh 7 64/32 070000h-07ffffh 038000h-03ffffh 6 64/32 060000h-06ffffh 030000h-037fffh 5 64/32 050000h-05ffffh 028000h-02ffffh 4 64/32 040000h-04ffffh 020000h-027fffh 3 64/32 030000h-03ffffh 018000h-01ffffh 2 64/32 020000h-02ffffh 010000h-017fffh 1 64/32 010000h-01ffffh 008000h-00ffffh 0 64/32 000000h-00ffffh 000000h-007fffh table 19. top boot block addresses, m29w320dt (continued)
block addresses m29w320dt, m29w320db 42/56 table 20. bottom boot block addresses, m29w320db # size (kbyte/kword) address range (x8) address range (x16) 66 64/32 3f0000h-3fffffh 1f8000h-1fffffh 65 64/32 3e0000h-3effff h 1f0000h-1f7fffh 64 64/32 3d0000h-3dffff h 1e8000h-1effffh 63 64/32 3c0000h-3cffff h 1e0000h-1e7fffh 62 64/32 3b0000h-3bffffh 1d8000h-1dffffh 61 64/32 3a0000h-3affffh 1d0000h-1d7fffh 60 64/32 390000h-39ffffh 1c8000h-1cffffh 59 64/32 380000h-18ffffh 1c0000h-1c7fffh 58 64/32 370000h-37ffffh 1b8000h-1bffffh 57 64/32 360000h-36ffffh 1b0000h-1b7fffh 56 64/32 350000h-35ffffh 1a8000h-1affffh 55 64/32 340000h-34ffffh 1a0000h-1a7fffh 54 64/32 330000h-33ffffh 198000h-19ffffh 53 64/32 320000h-32ffffh 190000h-197fffh 52 64/32 310000h-31ffffh 188000h-18ffffh 51 64/32 300000h-30ffffh 180000h-187fffh 50 64/32 2f0000h-2fffffh 178000h-17ffffh 49 64/32 2e0000h-2eff ffh 170000h-177fffh 48 64/32 2d0000h-2dff ffh 168000h-16ffffh 47 64/32 2c0000h-2cff ffh 160000h-167fffh 46 64/32 2b0000h-2bff ffh 158000h-15ffffh 45 64/32 2a0000h-2aff ffh 150000h-157fffh 44 64/32 290000h-29ffffh 148000h-14ffffh 43 64/32 280000h-28ffffh 140000h-147fffh 42 64/32 270000h-27ffffh 138000h-13ffffh 41 64/32 260000h-26ffffh 130000h-137fffh 40 64/32 250000h-25ffffh 128000h-12ffffh 39 64/32 240000h-24ffffh 120000h-127fffh 38 64/32 230000h-23ffffh 118000h-11ffffh 37 64/32 220000h-22ffffh 110000h-117fffh 36 64/32 210000h-21ffffh 108000h-10ffffh 35 64/32 200000h-20ffffh 100000h-107fffh 34 64/32 1f0000h-1fffffh 0f8000h-0fbfffh 33 64/32 1e0000h-1effff h 0f0000h-0f7fffh
m29w320dt, m29w320db block addresses 43/56 32 64/32 1d0000h-1dffff h 0e8000h-0effffh 31 64/32 1c0000h-1cffff h 0e0000h-0e7fffh 30 64/32 1b0000h-1bffffh 0d8000h-0dffffh 29 64/32 1a0000h-1affffh 0d0000h-0d7fffh 28 64/32 190000h-19ffffh 0c8000h-0cffffh 27 64/32 180000h-18ffffh 0c0000h-0c7fffh 26 64/32 170000h-17ffffh 0b8000h-0bffffh 25 64/32 160000h-16ffffh 0b0000h-0b7fffh 24 64/32 150000h-15ffffh 0a8000h-0affffh 23 64/32 140000h-14ffffh 0a0000h-0a7fffh 22 64/32 130000h-13ffffh 098000h-09ffffh 21 64/32 120000h-12ffffh 090000h-097fffh 20 64/32 110000h-11ffffh 088000h-08ffffh 19 64/32 100000h-10ffffh 080000h-087fffh 18 64/32 0f0000h-0fffffh 078000h-07ffffh 17 64/32 0e0000h-0eff ffh 070000h-077fffh 16 64/32 0d0000h-0dff ffh 068000h-06ffffh 15 64/32 0c0000h-0cff ffh 060000h-067fffh 14 64/32 0b0000h-0bff ffh 058000h-05ffffh 13 64/32 0a0000h-0aff ffh 050000h-057fffh 12 64/32 090000h-09ffffh 048000h-04ffffh 11 64/32 080000h-08ffffh 040000h-047fffh 10 64/32 070000h-07ffffh 038000h-03ffffh 9 64/32 060000h-06ffffh 030000h-037fffh 8 64/32 050000h-05ffffh 028000h-02ffffh 7 64/32 040000h-04ffffh 020000h-027fffh 6 64/32 030000h-03ffffh 018000h-01ffffh 5 64/32 020000h-02ffffh 010000h-017fffh 4 64/32 010000h-01ffffh 008000h-00ffffh 3 32/16 008000h-00ffffh 004000h-007fffh 2 8/4 006000h-007fffh 003000h-003fffh 1 8/4 004000h-005fffh 002000h-002fffh 0 16/8 000000h-003fff h 000000h-001fffh table 20. bottom boot block addresses, m29w320db (continued)
common flash interface (cfi) m29w320dt, m29w320db 44/56 appendix b common flash interface (cfi) the common flash interface is a jedec approved, standardized data structure that can be read from the flash memory device. it allows a system software to query the device to determine various electrical and timing pa rameters, density information and functions supported by the memory. the system can interface easily with the device, enabling the software to upgrade itself when necessary. when the cfi query command is issued the device enters cfi query mode and the data structure is read from the memory. ta b l e 2 1 , ta b l e 2 2 , ta b l e 2 3 , ta b l e 2 4 , ta bl e 2 5 and ta bl e 2 6 show the addresses used to retrieve the data. the cfi data structure also contains a security area where a 64 bit unique security number is written (see ta bl e 2 6 , security code area). this area can be accessed only in read mode by the final user. it is impossible to change the security number after it has been written by numonyx. issue a read command to return to read mode. table 21. query structure overview (1) address sub-section name description x16 x8 10h 20h cfi query identification string command set id and algorithm data offset 1bh 36h system interface information device timing & voltage information 27h 4eh device geometry definition flash device layout 40h 80h primary algorithm-specific extended query table additional information specific to the primary algorithm (optional) 61h c2h security code area 64 bit unique device number 1. query data are always presented on the lowest order data outputs. table 22. cfi query identification string (1) address data description value x16 x8 10h 20h 0051h ?q? 11h 22h 0052h query unique ascii string "qry" "r" 12h 24h 0059h "y" 13h 26h 0002h primary algorithm command set and control interface id code 16 bit id code defining a specific algorithm amd compatible 14h 28h 0000h 15h 2ah 0040h address for primary algorithm extended query table (see ta b l e 2 4 ) p = 40h 16h 2ch 0000h 17h 2eh 0000h alternate vendor command set and control interface id code second vendor - specified algorithm supported na 18h 30h 0000h 19h 32h 0000h address for alternate algorithm extended query table na 1ah 34h 0000h 1. query data are always presented on the lowest or der data outputs (dq7-dq0) only. dq8-dq15 are ?0?.
m29w320dt, m29w320db common flash interface (cfi) 45/56 table 23. cfi query system interface information address data description value x16 x8 1bh 36h 0027h v cc logic supply minimum program/erase voltage bit 7 to 4bcd value in volts bit 3 to 0bcd value in 100 mv 2.7v 1ch 38h 0036h v cc logic supply maximum program/erase voltage bit 7 to 4bcd value in volts bit 3 to 0bcd value in 100 mv 3.6v 1dh 3ah 00b5h v pp [programming] supply minimum program/erase voltage bit 7 to 4hex value in volts bit 3 to 0bcd value in 100 mv 11.5v 1eh 3ch 00c5h v pp [programming] supply maximum program/erase voltage bit 7 to 4hex value in volts bit 3 to 0bcd value in 100 mv 12.5v 1fh 3eh 0004h typical timeout per single byte/word program = 2 n s 16s 20h 40h 0000h typical timeout for minimum size write buffer program = 2 n s na 21h 42h 000ah typical timeout per individual block erase = 2 n ms 1s 22h 44h 0000h typical timeout for full chip erase = 2 n ms na 23h 46h 0005h maximum timeout for byte/word program = 2 n times typical 512s 24h 48h 0000h maximum timeout for write buffer program = 2 n times typical na 25h 4ah 0004h maximum timeout per individual block erase = 2 n times typical 16s 26h 4ch 0000h maximum timeout for chip erase = 2 n times typical na table 24. device geometry definition address data description value x16 x8 27h 4eh 0016h device size = 2 n in number of bytes 4 mbyte 28h 29h 50h 52h 0002h 0000h flash device interface code description x8, x16 async. 2ah 2bh 54h 56h 0000h 0000h maximum number of bytes in multi-byte program or page = 2 n na 2ch 58h 0004h number of erase block regions within the device. it specifies the number of region s within the device containing contiguous erase blocks of the same size. 4 2dh 2eh 5ah 5ch 0000h 0000h region 1 information number of identical size erase block = 0000h+1 1 2fh 30h 5eh 60h 0040h 0000h region 1 information block size in region 1 = 0040h * 256 byte 16 kbyte
common flash interface (cfi) m29w320dt, m29w320db 46/56 31h 32h 62h 64h 0001h 0000h region 2 information number of identical size erase block = 0001h+1 2 33h 34h 66h 68h 0020h 0000h region 2 information block size in region 2 = 0020h * 256 byte 8 kbyte 35h 36h 6ah 6ch 0000h 0000h region 3 information number of identical size erase block = 0000h+1 1 37h 38h 6eh 70h 0080h 0000h region 3 information block size in region 3 = 0080h * 256 byte 32 kbyte 39h 3ah 72h 74h 003eh 0000h region 4 information number of identical-size erase block = 003eh+1 63 3bh 3ch 76h 78h 0000h 0001h region 4 information block size in region 4 = 0100h * 256 byte 64 kbyte table 24. device geometry definition (continued) address data description value x16 x8 table 25. primary algorithm-specific extended query table address data description value x16 x8 40h 80h 0050h primary algorithm extended query table unique ascii string ?pri? "p" 41h 82h 0052h "r" 42h 84h 0049h "i" 43h 86h 0031h major version number, ascii "1" 44h 88h 0030h minor version number, ascii "0" 45h 8ah 0000h address sensitive unlock (bits 1 to 0) 00 = required, 01= not required silicon revision number (bits 7 to 2) ye s 46h 8ch 0002h erase suspend 00 = not supported, 01 = read only, 02 = read and write 2 47h 8eh 0001h block protection 00 = not supported, x = number of blocks in per group 1 48h 90h 0001h temporary block unprotect 00 = not supported, 01 = supported ye s 49h 92h 0004h block protect /unprotect 04 = m29w400b 4 4ah 94h 0000h simultaneous operations, 00 = not supported no 4bh 96h 0000h burst mode, 00 = not supported, 01 = supported no 4ch 98h 0000h page mode, 00 = not supported, 01 = 4 page word, 02 = 8 page word no
m29w320dt, m29w320db common flash interface (cfi) 47/56 4dh 9ah 00b5h v pp supply minimum program/erase voltage bit 7 to 4 hex value in volts bit 3 to 0 bcd value in 100 mv 11.5v 4eh 9ch 00c5h v pp supply minimum program/erase voltage bit 7 to 4 hex value in volts bit 3 to 0 bcd value in 100 mv 12.5v 4fh 9eh 000xh top/bottom boot block flag 02h = bottom boot device, 03h = top boot device ? table 25. primary algorithm-specific extended query table (continued) address data description value x16 x8 table 26. security code area address data description x16 x8 61h c3h, c2h xxxx 64 bit: unique device number 62h c5h, c4h xxxx 63h c7h, c6h xxxx 64h c9h, c8h xxxx
block protection m29w320dt, m29w320db 48/56 appendix c block protection block protection can be used to prevent any operation from modifying the data stored in the flash. each block can be protected individually. once protected, program and erase operations on the block fail to change the data. there are three techniques that can be used to control block protection, these are the programmer technique, the in-system technique and temporary unprotection. temporary unprotection is controlled by the reset/block temporary unprotection pin, rp ; this is described in the signal descriptions section. unlike the command interface of the program/erase controller, the techniques for protecting and unprotecting blocks change between different flash memory suppliers. for example, the techniques for amd parts will not work on numonyx parts. care should be taken when changing drivers for one part to work on another. c.1 programmer technique the programmer technique uses high (v id ) voltage levels on some of the bus pins. these cannot be achieved using a standard microprocessor bus, therefore the technique is recommended only for use in programming equipment. to protect a block follow the flowchart in figure 16: programmer equipment block protect flowchart . to unprotect the whole chip it is necessary to protect all of the blocks first, then all blocks can be unprotected at the same time. to unprotect the chip follow figure 17: programmer equipment chip unprotect flowchart . table 27: programmer technique bus operations, byte = v ih or v il , gives a summary of each operation. the timing on these flowcharts is critical. care should be taken to ensure that, where a pause is specified, it is followed as closely as possible. do not abort the procedure before reaching the end. chip unprotect can take several seconds and a user message should be provided to show that the operation is progressing. c.2 in-system technique the in-system technique requires a high voltage level on the reset/blocks temporary unprotect pin, rp . this can be achieved without violating the maximum ratings of the components on the microprocessor bus, therefore this technique is suitable for use after the flash has been fitted to the system. to protect a block follow the flowchart in figure 18: in-system equipment block protect flowchart . to unprotect the whole chip it is necessary to protect all of the blocks first, then all the blocks can be unprotected at the same time. to unprotect the chip follow figure figure 19: in-system equipment chip unprotect flowchart . the timing on these flowcharts is critical. care should be taken to ensure that, where a pause is specified, it is followed as closely as possible. do not allow the microprocessor to service interrupts that will upset the timing a nd do not abort the proc edure before reaching the end. chip unprotect can take several seconds and a user message should be provided to show that the operation is progressing.
m29w320dt, m29w320db block protection 49/56 table 27. programmer technique bus operations, byte = v ih or v il operation e g w address inputs a0-a20 data inputs/outputs dq15a?1, dq14-dq0 block protect v il v id v il pulse a9 = v id , a12-a20 block address others = x x chip unprotect v id v id v il pulse a9 = v id , a12 = v ih , a15 = v ih others = x x block protection verify v il v il v ih a0 = v il , a1 = v ih , a6 = v il , a9 = v id , a12-a20 block address others = x pass = xx01h retry = xx00h block unprotection verify v il v il v ih a0 = v il , a1 = v ih , a6 = v ih , a9 = v id , a12-a20 block address others = x retry = xx01h pass = xx00h
block protection m29w320dt, m29w320db 50/56 figure 16. programmer equipment block protect flowchart address = block address ai03469 g, a9 = v id , e = v il n = 0 wait 4s wait 100s w = v il w = v ih e, g = v ih , a0, a6 = v il , a1 = v ih a9 = v ih e, g = v ih ++n = 25 start fail pass yes no data = 01h yes no w = v ih e = v il wait 4s g = v il wait 60ns read data verify protect set-up end a9 = v ih e, g = v ih
m29w320dt, m29w320db block protection 51/56 figure 17. programmer equipment chip unprotect flowchart protect all blocks ai03470 a6, a12, a15 = v ih (1) e, g, a9 = v id data w = v ih e, g = v ih address = current block address a0 = v il , a1, a6 = v ih wait 10ms = 00h increment current block n = 0 current block = 0 wait 4s w = v il ++n = 1000 start yes yes no no last block yes no e = v il wait 4s g = v il wait 60ns read data fail pass verify unprotect set-up end a9 = v ih e, g = v ih a9 = v ih e, g = v ih
block protection m29w320dt, m29w320db 52/56 figure 18. in-system equipment block protect flowchart ai03471 write 60h address = block address a0 = v il , a1 = v ih , a6 = v il n = 0 wait 100s write 40h address = block address a0 = v il , a1 = v ih , a6 = v il rp = v ih ++n = 25 start fail pass yes no data = 01h yes no rp = v ih wait 4s verify protect set-up end read data address = block address a0 = v il , a1 = v ih , a6 = v il rp = v id issue read/reset command issue read/reset command write 60h address = block address a0 = v il , a1 = v ih , a6 = v il
m29w320dt, m29w320db block protection 53/56 figure 19. in-system equipment chip unprotect flowchart ai03472 write 60h any address with a0 = v il , a1 = v ih , a6 = v ih n = 0 current block = 0 wait 10ms write 40h address = current block address a0 = v il , a1 = v ih , a6 = v ih rp = v ih ++n = 1000 start fail pass yes no data = 00h yes no rp = v ih wait 4s read data address = current block address a0 = v il , a1 = v ih , a6 = v ih rp = v id issue read/reset command issue read/reset command protect all blocks increment current block last block yes no write 60h any address with a0 = v il , a1 = v ih , a6 = v ih verify unprotect set-up end
revision history m29w320dt, m29w320db 54/56 10 revision history table 28. document revision history date revision changes march-2001 -01 first issue (brief data) 08-jun-2001 -02 document expanded to full product preview 22-jun-2001 -03 minor text corrections to read/reset and read cfi commands and status register error and toggle bits. 27-jul-2001 -04 document type: from product preview to preliminary data tfbga connections and block addresses (x16) diagrams clarification write protect and block unprotect clarification cfi primary algorithm table, block protection change 05-oct-2001 -05 added block protection appendix ?write protect/v pp ? pin renamed to ?v pp /write protect? to be consistent with abbreviation. changes to the v pp /wp pin description, figure 13 and ta bl e 1 5 . i pp added to ta b l e 1 1 and i cc3 clarified. modified description of v pp /wp operation in unlock bypass command section. added v pp /wp decoupling capacitor to figure figure 1 . clarified read/reset operation during erase suspend. 07-feb-2002 -06 tfbga package changed from 48 ball to 63 ball 05-apr-2002 -07 description of ready/busy signal clarified (and figure 12 modified) clarified allowable commands during block erase clarified the mode the device returns to in the cfi read query command section 19-nov-2002 7.1 erase suspend latency time (typical and maximum) added to program, erase times and program, erase endurance cycles table. typical values added for icc1 and icc2 in dc characteristics table. logic diagram and data toggle flowchart corrected. revision numbering modified: a minor revision will be indicated by incrementing the digit after the dot, and a major revision, by incrementing the digit before the dot (revision version 07 equals 7.0). document promoted to full datasheet. 26-may-2003 7.2 data retention added to table 6: program, erase times and program, erase endurance cycles , and typical after 100k w/e cycles column removed. tsop48 package mechanical updated. lead-free package options e and f added to table 18: ordering information scheme . 16-aug-2005 8.0 tfbga48 package added throughout document.
m29w320dt, m29w320db revision history 55/56 13-jun-2006 9 document title modified. tfbga63 package removed. ecopack text added. rb signal updated in figure 12: reset/block temporary unprotect ac waveforms . t plyh updated in table 15: reset/block temporary unprotect ac characteristics . in table 7: status register bits , dq7 changed to dq7 for program, program during erase suspend and program error. 26-mar-2008 10 applied numonyx branding. table 28. document revision history (continued) date revision changes
m29w320dt, m29w320db 56/56 please read carefully: information in this document is provided in connection with numonyx? products. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. except as provided in numonyx's terms and conditions of sale for such products, numonyx assumes no liability whatsoever, and numonyx disclaims any express or implied warranty, relating to sale and/or use of numonyx products including liability or warranties re lating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. numonyx products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in n uclear facility applications. numonyx may make changes to specifications and product descriptions at any time, without notice. numonyx, b.v. may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights th at relate to the presented subject matter. the furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. designers must not rely on the absence or characteristics of any features or instructions marked ?reserved? or ?undefined.? num onyx reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. contact your local numonyx sales office or your distributor to obtain the latest specifications and before placing your product order. copies of documents which have an order number and are referenced in this document, or other numonyx literature may be obtained by visiting numonyx's website at http://www.numonyx.com . numonyx strataflash is a trademark or registered trademark of numonyx or its subsidiaries in the united states and other countr ies. *other names and brands may be claimed as the property of others. copyright ? 11/5/7, numonyx, b.v., all rights reserved.

▲Up To Search▲

Price & Availability of M29W320DB70ZE1F

	To Download M29W320DB70ZE1F Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .